Conflict detection and resolution in an abr network

ABSTRACT

A scheme for managing conflict resolution in an ABR streaming environment with respect to a bandwidth pipe serving a customer premises. In one aspect, when a session request is received from a new ABR client launched in the customer premises that includes one or more existing ABR clients having corresponding streaming sessions, a bandwidth forecasting module is configured to forecast bandwidth requirements with respect to the corresponding ABR streaming sessions after accounting for a bandwidth requirement for the new ABR client&#39;s session request. A conflict may be detected if any of forecasted bandwidth requirements violates a bitrate threshold policy relative to the corresponding ABR streaming sessions and/or the new session being requested. If there is a conflict, a conflict notification message to the new ABR client is provided and the session request from the new ABR client is rejected.

REFERENCE TO RELATED APPLICATION(S)

This application discloses subject matter that is related to the subjectmatter of the following U.S. patent application(s): (i) “BANDWIDTHMANAGEMENT FOR OVER-THE-TOP ADAPTIVE STREAMING” (Ericsson Ref. No.:P39592-US1), application Ser. No. 13/845,320 filed Mar. 18, 2013, in thename(s) of Christopher Phillips et al., (ii) “REGULATING CONTENT STREAMSFROM A WEIGHTED FAIR QUEUING SCHEDULER USING WEIGHTS DEFINED FOR USEREQUIPMENT NODES” (Ericsson Ref. No.: P37772-US1), application Ser. No.13/597,333 filed Aug. 29, 2012, in the name(s) of Christopher Phillipset al., (iii) “METHODS AND APPARATUS FOR MANAGING NETWORK RESOURCES USEDBY MULTIMEDIA STREAMS IN A VIRTUAL PIPE” (Ericsson Ref. No.:P36357-US1), application Ser. No. 13/403,075 filed Feb. 23, 2012, in thename(s) of Christopher Phillips et al., and (iv) “METHODS, APPARATUS,AND COMPUTER PROGRAM PRODUCTS FOR ALLOCATING BANDWIDTH FOR PUSH AND PULLCONTENT REQUESTS IN A CONTENT DELIVERY NETWORK” (Ericsson Ref. No.:P39663-US1), application Ser. No. 13/856,895, filed Apr. 4, 2013, in thename(s) of Christopher Phillips et al., each of which is herebyincorporated by reference in its entirety. The subject matter of thepresent patent application is also related to the subject matter of thefollowing U.S. patent application(s) filed even date herewith: (i)“CONFLICT DETECTION AND RESOLUTION IN AN ABR NETWORK USING CLIENTINTERACTIVITY” (Ericsson Ref. No.: P42767-US1), application Ser. No.______, in the name(s) of Christopher Phillips et al., which is herebyincorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to communication networks. Moreparticularly, and not by way of any limitation, the present disclosureis directed to a scheme for effectuating conflict detection andresolution in an adaptive bitrate (ABR) streaming environment.

BACKGROUND

A content delivery network or CDN (sometimes also referred to as acontent distribution network) typically distributes content in a “besteffort” fashion across the nodes throughout a network using technologiessuch as ABR streaming. It is known, however, that ABR can result inunfair and sometimes incongruous apportionment of bandwidth on a networkbased upon the order multiple clients begin to use a network resource.Since the bandwidth usage is typically determined by a client requestingthe content, and because ABR clients can be opportunistic, they maybecome greedy, thereby affecting the overall bandwidth quality of abandwidth pipe. Although current ABR systems allow bandwidth to be“adapted” to existing network conditions, such solutions continue to bedeficient relative to more realistic content consumption environments.

SUMMARY

The present patent disclosure is broadly directed to systems, methods,apparatuses, devices, and associated non-transitory computer-readablemedia for managing conflict resolution in an ABR streaming environmentwith respect to a bandwidth pipe serving a customer premises. In oneembodiment, a method is disclosed that comprises, inter alia, thefollowing features: receiving a session request from a new ABR clientlaunched in the customer premises that includes one or more existing ABRclients, wherein each existing ABR client is engaged in a correspondingABR streaming session; forecasting bandwidth requirements for the one ormore existing ABR clients with respect to the corresponding ABRstreaming sessions after accounting for a bandwidth requirement for thenew ABR client's session request; detecting or otherwise determining aconflict condition (e.g., an impending conflict) if any of forecastedbandwidth requirements violates a bitrate threshold policy relative tothe corresponding ABR streaming sessions of the existing ABR clients;and if there is a conflict, providing a conflict notification message(e.g., a video-encoded still image of a suitable message) to the new ABRclient and rejecting the session request from the new ABR client.

In another aspect, an embodiment of a system for managing conflictresolution in an ABR streaming environment is disclosed. The claimedembodiment comprises, inter alia, a back office operative to receive asession request from a new ABR client launched by a client device in thecustomer premises that includes one or more existing ABR clients,wherein each existing ABR client is engaged in a corresponding ABRstreaming session. A subscriber policy management node is provided thatis operative to request, responsive to a message from the back office,one of a premises gateway and a CDN edge delivery node for forecastedbandwidth requirements of the one or more existing ABR clients withrespect to the corresponding ABR streaming sessions after accounting fora bandwidth requirement for the new ABR client's session request. Thesubscriber policy management node is further operative to detect orotherwise determine a conflict condition (potential or otherwise) if anyof forecasted bandwidth requirements violates a bitrate threshold policyrelative to the corresponding ABR streaming sessions of the existing ABRclients. A conflict management node is operative, responsive to aconflict detection or determination message from the subscriber policymanagement node, to generate a conflict message encoding request to avideo message system for facilitating transmission of a still image of aconflict notification message to the new ABR client that the sessionrequest from the new ABR client is being rejected on account of abandwidth conflict.

In another aspect, an embodiment of a premises gateway configured tomanage a bandwidth pipe serving a customer premises is disclosed. Theclaimed embodiment comprises, inter alia, one or more processors; and abitrate forecasting module coupled to the one or more processors,wherein the bitrate forecasting module includes instructions executableby one or more processors and configured to perform or otherwiseeffectuate the following in conjunction with the processor(s): forecastbandwidth requirements, responsive to a request from a subscriber policymanagement node, for one or more existing ABR clients of a customerpremises with respect to corresponding ABR streaming sessions afteraccounting for a bandwidth requirement of a new ABR client's request forinitiating a new streaming session on a client device; and generate abandwidth forecast response message to the subscriber policy managementnode, the bandwidth forecast response message including bitratesforecasted for the existing ABR streaming sessions and/or the requestednew streaming session based at least in part upon priority weightsassociated with the existing ABR streaming sessions and the requestednew streaming session. Similarly, in a related aspect, an embodiment ofan edge delivery node is disclosed that includes a bitrate forecastingmodule configured to facilitate the functionalities set forthhereinabove, mutatis mutandis.

In a still further aspect, another embodiment of a method for managingconflict resolution is disclosed. The claimed embodiment comprises,inter alia, the following features: receiving a session request from anew ABR client launched in the customer premises that includes one ormore existing ABR clients, wherein each existing ABR client is engagedin a corresponding ABR streaming session; forecasting bandwidthrequirements for the one or more existing ABR clients with respect tothe corresponding ABR streaming sessions after accounting for abandwidth requirement for the new ABR client's session request;detecting or otherwise determining a conflict condition if any offorecasted bandwidth requirements violates a bitrate threshold policyrelative to the corresponding ABR streaming sessions of the existing ABRclients; launching an interactive session with at least one of the newABR client and an existing ABR client with respect to the sessionrequest; presenting a dialog to a user of the at least one of the newABR client and an existing ABR client, the dialog for offering one ormore options to the user relative to the session request; and acceptingan option input by the user and effectuating an action responsive to theoption.

In a related embodiment, a system for managing conflict resolution withrespect to a new ABR client is disclosed, comprising, inter alia, aconflict management node that is operative, responsive to a conflictdetection message from a subscriber policy management node, to performor effectuate the following features: facilitate launching of aninteractive session with at least one of the new ABR client and anexisting ABR client with respect to the new ABR client's sessionrequest; present a dialog to a user of the at least one of the new ABRclient and an existing ABR client, the dialog for offering one or moreoptions to the user relative to the session request; and accept anoption input by the user and effectuate an action responsive to theoption. Additionally, the subscriber policy management node of theclaimed embodiment is operative responsive to a back office message(e.g., a policy request message relative to the new ABR client's sessionrequest), similar to one or more embodiments described above, rnutatismutandis.

In still further aspects, one or more embodiments of a non-transitorycomputer-readable medium containing computer-executable programinstructions or code portions stored thereon are disclosed forperforming one or more embodiments of the methods set forth above whenexecuted by a processor of a network node, element, gateway, and thelike.

Advantages of the present invention include, but not limited to,providing greater transparency and control to end users with respect tothe consumption of ABR assets in a streaming environment havingpotential conflicts. The embodiments may allow users to overridestanding policies and control how conflicts in policies are notified andresolved. In legacy client applications, at least some embodiments allowthe inventive features of the present application to be implementedregardless of existing technology, thereby facilitating fairlyinexpensive and more universal rollout of the inventive technology. Withrespect to custom client applications, the inventive features allow userinteractivity, providing a more robust and customer-focused experiencein resolving bandwidth conflicts. Further features of the variousembodiments are as claimed in the dependent claims. Additional benefitsand advantages of the embodiments will be apparent in view of thefollowing description and accompanying Figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure are illustrated by way of example,and not by way of limitation, in the Figures of the accompanyingdrawings in which like references indicate similar elements. It shouldbe noted that different references to “an” or “one” embodiment in thisdisclosure are not necessarily to the same embodiment, and suchreferences may mean at least one. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

The accompanying drawings are incorporated into and form a part of thespecification to illustrate one or more exemplary embodiments of thepresent disclosure. Various advantages and features of the disclosurewill be understood from the following Detailed Description taken inconnection with the appended claims and with reference to the attacheddrawing Figures in which:

FIG. 1A depicts an example ABR streaming network arrangement including acontent delivery network (CDN) and an ABR network back officeenvironment wherein one or more embodiments of the present patentapplication may be practiced;

FIG. 1B depicts an example customer premises having one or more ABRstreaming clients and a plurality of network elements that may beconfigured to manage conflict resolution in an ABR streaming environmentwith respect to a bandwidth pipe serving the customer premises;

FIGS. 2-5 depict flowcharts of various blocks, steps and/or acts thatmay be combined in one or more arrangements that illustrate exampleconflict detection and resolution methods according to one or moreembodiments of the present patent disclosure;

FIG. 6 depicts an example ABR streaming environment with additionaldetails for practicing an embodiment of the present patent disclosure:

FIG. 7 depicts a flowchart of various blocks, steps and/or actsillustrative of additional details with respect to an embodiment of aconflict detection scheme according to an embodiment of the presentpatent disclosure;

FIG. 8 depicts the example ABR streaming environment of FIG. 6 withadditional details relative to an embodiment of a conflict resolutionscheme according to an embodiment of the present patent disclosure;

FIG. 9 depicts a flowchart of various blocks, steps and/or actsillustrative of additional details with respect to an embodiment of aconflict resolution scheme according to an embodiment of the presentpatent disclosure;

FIG. 10 depicts the example ABR streaming environment of FIG. 6 withadditional details relative to an embodiment of a conflict resolutionscheme according to another embodiment of the present patent disclosure;

FIG. 11 depicts a flowchart of various blocks, steps and/or actsillustrative of additional details with respect to another embodiment ofa conflict resolution scheme according to an embodiment of the presentpatent disclosure;

FIG. 12 depicts an embodiment of the example ABR streaming environmentof FIG. 6 wherein certain aspects of conflict detection/resolution maybe practiced at a premises gateway;

FIG. 13 depicts an embodiment of the example ABR streaming environmentof FIG. 6 wherein certain aspects of conflict detection/resolution maybe practiced at a CDN node; and

FIG. 14 depicts a block diagram of an example element configured toexecute certain aspects of conflict detection/resolution according toone or more embodiments of the present patent application.

DETAILED DESCRIPTION OF THE DRAWINGS

In the following description, numerous specific details are set forthwith respect to one or more embodiments of the present patentdisclosure. However, it should be understood that one or moreembodiments may be practiced without such specific details. In otherinstances, well-known circuits, subsystems, components, structures andtechniques have not been shown in detail in order not to obscure theunderstanding of the example embodiments. Accordingly, it will beappreciated by one skilled in the art that the embodiments of thepresent disclosure may be practiced without such specific components. Itshould be further recognized that those of ordinary skill in the art,with the aid of the Detailed Description set forth herein and takingreference to the accompanying drawings, will be able to make and use oneor more embodiments without undue experimentation,

Additionally, terms such as “coupled” and “connected,” along with theirderivatives, may be used in the following description, claims, or both.It should be understood that these terms are not necessarily intended assynonyms for each other. “Coupled” may be used to indicate that two ormore elements, which may or may not be in direct physical or electricalcontact with each other, co-operate or interact with each other.“Connected” may be used to indicate the establishment of communication,i.e., a communicative relationship, between two or more elements thatare coupled with each other. Further, in one or more example embodimentsset forth herein, generally speaking, an element, component or modulemay be configured to perform a function if the element is capable ofperforming or otherwise structurally arranged to perform that function.

As used herein, a network element or node may be comprised of one ormore pieces of service network equipment, including hardware andsoftware that communicatively interconnects other equipment on a network(e.g., other network elements, end stations, etc.), and is adapted tohost one or more applications or services with respect to a plurality ofsubscribers. Some network elements may comprise “multiple servicesnetwork elements” that provide support for multiple network-basedfunctions (e.g., A/V media management, session control, Quality ofService (QoS) policy enforcement, bandwidth scheduling management,subscriber/device policy and profile management, content providerpriority policy management, streaming policy management, conflictmanagement, and the like), in addition to providing support for multipleapplication services (e.g., data and multimedia applications).Subscriber end stations or client devices may comprise any deviceconfigured to execute, inter alia, a streaming client application (e.g.,an ABR streaming client application) for receiving content from one ormore content providers. Accordingly, such client devices may includeset-top boxes, PVR/DVRs, workstations, laptops, netbooks, palm tops,mobile phones, smartphones, multimedia phones, Voice Over InternetProtocol (VOIP) phones, mobile/wireless user equipment, high definitionTV terminals, portable media players, gaming systems or consoles (suchas the Wii®, Play Station 3®, Xbox 360®), etc., that may access orconsume content/services provided over a content delivery network forpurposes of one or more embodiments set forth herein. Further, theclient devices may also access or consume content/services provided overbroadcast networks (e.g., cable and satellite networks) as well as apacket-switched wide area public network such as the Internet viasuitable service provider access networks. In a still further variation,the client devices or subscriber end stations may also access or consumecontent/services provided on virtual private networks (VPNs) overlaid on(e.g., tunneled through) the Internet.

One or more embodiments of the present patent disclosure may beimplemented using different combinations of software, firmware, and/orhardware. Thus, one or more of the techniques shown in the Figures(e.g., flowcharts) may be implemented using code and data stored andexecuted on one or more electronic devices or nodes (e.g., a subscriberclient device or end station, a network element, etc.). Such electronicdevices may store and communicate (internally and/or with otherelectronic devices over a network) code and data using computer-readablemedia, such as non-transitory computer-readable storage media (e.g.,magnetic disks, optical disks, random access memory, read-only memory,flash memory devices, phase-change memory, etc.), transitorycomputer-readable transmission media (e.g., electrical, optical,acoustical or other form of propagated signals—such as carrier waves,infrared signals, digital signals), etc. In addition, such networkelements may typically include a set of one or more processors coupledto one or more other components, such as one or more storage devices(e.g., non-transitory machine-readable storage media) as well as storagedatabase(s), user input/output devices (e.g., a keyboard, a touchscreen, a pointing device, and/or a display), and network connectionsfor effectuating signaling and/or bearer media transmission. Thecoupling of the set of processors and other components may be typicallythrough one or more buses and bridges (also termed as bus controllers),arranged in any known (e.g., symmetric/shared multiprocessing) orheretofore unknown architectures. Thus, the storage device or componentof a given electronic device or network element may be configured tostore code and/or data for execution on one or more processors of thatelement, node or electronic device for purposes of implementing one ormore techniques of the present disclosure.

Referring now to the drawings and more particularly to FIG. 1A, depictedtherein is an example ABR streaming network environment 100A including acontent delivery network or content distribution network (CDN) 140 and astreaming network back office infrastructure 122 wherein one or moreembodiments of the present patent application may be practiced. Forpurposes of the present patent application, CDN 140 may comprise anoverlay network architected for high-performance streaming of a varietyof digital assets or program assets as well as services (hereinafterreferred to as “content”) to subscribers using one or moreInternet-based infrastructures, private/dedicated infrastructures or acombination thereof. In general, the terms “content” or “content file”as used in reference to at least some embodiments of the present patentdisclosure may include digital assets and program assets such as anytype of audio/video content or program segment, streaming or static(e.g., recorded over-the-air free network television (TV) shows orprograms, pay TV broadcast programs via cable networks or satellitenetworks, free-to-air satellite TV shows, IPTV programs, etc.),Over-The-Top (OTT) and video-on-demand (VOD) or movie-on-demand (MOD)shows or programs, time-shifted TV (TSTV) content, as well as othercontent assets provided by content publishers, owners or providers,including but not limited to software files, executable computer code orprograms, online electronic games, Internet radio shows/programs,entertainment programs, educational programs, movies, music videoprograms, and the like, that may be delivered using any known orheretofore unknown streaming technologies. By way of illustration,content delivered via CDN 140 using ABR streaming techniques may beencoded to support Microsoft® Silverlight® Smooth Streaming, HTTPstreaming (for instance, Dynamic Adaptive Streaming over HTTP or DASH,HTTP Live Streaming or HLS, HTTP Dynamic Streaming or HDS, etc.),Icecast, and so on. In general, the overlay architecture of CDN 140 mayinclude a multi-level, hierarchically-organized interconnected assemblyof network servers for providing media pathways or “pipes” from one ormore central distribution nodes to one or more levels of regionaldistribution nodes that are connected to one or more local edge serversconfigured to serve a plurality of end users or subscribers inrespective serving location areas. In addition to such “distributionservers” (sometimes also referred to as “surrogates”), CDN 140 may alsoinclude and/or interoperate with various network elements configured toeffectuate request redirection or rerouting mechanisms as well asrelated back office systems or nodes such as operator/subscriber policymanagement systems, bandwidth scheduling systems, account/billingsystems, and the like, that may be deployed as part of the associatedstreaming network back office infrastructure 122. As illustrated, anexample subscriber/operator management system 124 deployed in the backoffice infrastructure 122 may include an operator pipe and contentpolicy node 126, a subscriber device profile and priority definitionnode 128, in addition to a streaming policy server node 134, a billingnode 130 and a subscriber authentication node 136. A bandwidth decisionmanager 132 and a weighted fair queuing (WFQ) scheduler 138 may beconfigured to use data from the operator pipe and content policy node126 and the subscriber device profile and priority node 128 to regulatebandwidth allocated to the CDN distribution pipes for carrying groups ofcontent streams to the subscribers. Additional details with respect toallocating bandwidth on an outgoing CDN distribution pipe based onweights and priority levels associated with subscriber devices,content-based policies, dynamic resizing of the pipes using, e.g., oneor more pipe control nodes, and scheduling based on WFQ techniques, maybe found in one or more of the following commonly owned co-pending U.S.patent application(s): (i) “BANDWIDTH MANAGEMENT FOR OVER-THE-TOPADAPTIVE STREAMING” (Ericsson Ref. No.: P39592-US1), application Ser.No. 13/845,320 filed Mar. 18, 2013, in the name(s) of ChristopherPhillips et al., (ii) “REGULATING CONTENT STREAMS FROM A WEIGHTED FAIRQUEUING SCHEDULER USING WEIGHTS DEFINED FOR USER EQUIPMENT NODES”(Ericsson Ref. No.: P37772-US1), application Ser. No. 13/597,333 filedAug. 29, 2012, in the name(s) of Christopher Phillips et al., (iii)“METHODS AND APPARATUS FOR MANAGING NETWORK RESOURCES USED BY MULTIMEDIASTREAMS IN A VIRTUAL PIPE” (Ericsson Ref. No.: P36357-US1), applicationSer. No. 13/403,075 filed Feb. 23, 2012, in the name(s) of ChristopherPhillips et al., and (iv) “METHODS, APPARATUS, AND COMPUTER PROGRAMPRODUCTS FOR ALLOCATING BANDWIDTH FOR PUSH AND PULL CONTENT REQUESTS INA CONTENT DELIVERY NETWORK” (Ericsson Ref. No.: P39663-US1), applicationSer. No. 13/856,895, filed Apr. 4, 2013, in the name(s) of ChristopherPhillips et al., cross-referenced hereinabove and hereby incorporated byreference herein. In addition to the various subscriber/operator policymanagement and bandwidth scheduling functionalities set forth above, theback office infrastructure 122 may also comprise appropriate conflictdetection and management nodes or systems as will be described in detailhereinbelow.

Continuing to refer to FIG. 1A, reference numeral 102 refers to one ormore example client devices or user equipment (UE) devices that consumebandwidth provided via a bandwidth pipe associated with asubscriber/customer for consuming content delivered via CDN 140 in anytype or number of access technologies including broad band access viawired and/or wireless (radio) communications. As such, UE devices 102may be disposed as part of a content consumption environment served by asuitable ABR bandwidth pipe. For purposes of the present patentapplication, the terms “streaming client device” and “client device” maybe used synonymously and may comprise any UE device or appliance that inone implementation not only receives program assets for live viewing,playback and/or decoding the content, but also operates as a commandconsole or terminal that can accept user inputs, commands or requests tointeract with a network element disposed in CDN 140 and/or theassociated back office infrastructure 122 for requesting content thatmay be selectively rendered at one or more external audio/visual (A/V)devices 112-1 to 112-N. As such, UE devices 102 may be part of acustomer premises (e.g., a home, an enterprise or organization, etc.)that is served by a bandwidth pipe allocated thereto wherein differentdevices may be streaming various types/categories of content at the sametime or otherwise. Typically, such UE devices 102 may include one ormore streaming client modules or applications 104 (e.g., an ABRstreaming client application) and associated decoding functionalities108 depending on the streaming technologies implemented, each operatingin association with a processor module 106. An optional local display110 (which may also be referred to as an internal or included display)may have the capability to render the video content in one or moreresolutions (e.g., standard definition such as 480i, enhanced definitionsuch as 480p, or high definition such as 720p and up). Further, theclient devices 102 may also include appropriate structures and modulesfor obtaining identity information, capabilities information, etc. fromthe external A/V devices 112-1 to 112-N that may be used by thesubscriber/operator policy management system 124 for selecting and/orprovisioning appropriate bandwidth with respect to streaming aparticular content program requested by the subscriber.

By way of further illustration, external A/V devices 112-1 to 112-N maycomprise media rendering devices such as one or more high definition TV(HDTV) monitors with 1080i/1080p resolutions, one or more ultra highdefinition TV (UHDTV) monitors with 2160p, 4320p or 8640p resolutions,3D TV monitors, HD/UHD video/cinema projectors, HD/UHD computermonitors, HD/3D Blu-ray Disc (BD) players, and auxiliary gaming/homeentertainment displays, etc., that may be connected or communicativelycoupled to the client devices 102 via any suitable wired or wirelesstechnologies. Accordingly, reference numerals 120-1 to 120-N areillustrative of communication links between the client device 102 andthe respective external A/V devices (which sometimes may also bereferred to as “external rendering devices” or “connected displaydevices”) that may comprise High-Definition Media Interface (HDMI)connections, Digital Visual Interface or Digital Video Interface (DVI)connections, FireWire connections, HD wireless connections utilizingunlicensed radio frequencies in 5 GHz, 60 GHz or 190 GHz bands, wirelessHDTV (also referred to as WiDi) connections, Wireless Home DigitalInterface (WHDI) connections, Digital Living Network Alliance(DLNA)-compliant connections, as well as other proprietary connectionssuch as Apple® AirPlay connections, and the like. Depending on thefunctionality, an external A/V device may or may not include a decodingcapability, and may or may not include both audio and video renderingcapabilities. For purposes of illustration, external A/V devices 112-1to 112-N are each exemplified with respective decoder blocks 116-1 to116-N. Additionally, blocks 114-1 to 114-N are illustrative of storageareas of respective external A/V devices 112-1 to 112-N that containdisplay device information (DDI) including device identity information,rendering/decoding capabilities information and other information(collectively referred to as “external device information” or“metadata”). Example pieces of DDI may therefore comprise A/V device'smanufacturer name, serial number, product type, phosphor type, filtertype, supported A/V decoding and format information, display timinginformation, display screen size, display screen aspect ratio, luminancedata and pixel mapping data, among others. One skilled in the art willrecognize that storage areas 112-1 to 112-N may be implemented in anumber of ways including but not limited to, using persistent memorysuch as built-in or integrated read-only memory (ROM) circuits, erasableprogrammable read-only memory (EPROM) circuits, Flash memory circuits,as well as external memory cards, and the like, wherein the device datamay be downloaded, uploaded, updated, and/or reconfigured by third-partydevice vendors, via wireless means (over-the-air, for example) or overthe Internet.

In general operation, the client devices 102 and associated CDN and backoffice infrastructure 122/140 may be configured to effectuate adaptivestreaming of content as follows. Initially, source content is transcodedor otherwise encoded with different bit rates (e.g., multi-ratetranscoding). For example, a particular content may be transcoded intofive video files using variable bit rates, ranging from low to high bitrates. The particular content is therefore encoded as five different“versions” or “formats”, wherein each bit rate is called a profile orrepresentation. The encoded content is divided into fixed durationsegments or chunks, which are typically between two and ten seconds induration. One skilled in the art will recognize that shorter segmentsmay reduce coding efficiency whereas larger segments may impact theadaptability to changes in network throughput and/or fast changingclient behavior. Regardless of the chunk size, the segments may beGroup-of-Pictures (GOP)-aligned such that all encoding profiles have thesame segments. A suitable Manifest File is created that describes theencoding rates and Universal Resource Locator (URL) pointers relative tothe various segments of encoded content. In one implementation, theManifest File (MF), a Delivery Format (DF) and means for conversionfrom/to existing File Formats (FF) and Transport Streams (TS) may beprovided to a specific client device 102 when a particular content isrequested, which uses HTTP to fetch the encoded segments from thecontent provider network, provided there is no bandwidth conflict withrespect to the bandwidth pipe serving the premises. The receivedsegments may be buffered, as needed, and decoded and played back (i.e.,rendered) in sequence, either at the local display 110 or at any one orseveral of the external A/V devices (112-1 to 112-N). The ABR streamingclient module 104 may be designed to select an optimum profile of eachsegment so as to maximize quality without risking buffer underflow andstaffing (i.e., rebuffering) of the play-out. Each time the clientdevice 102 fetches a segment, it may choose the profile based on themeasured time to download the previous one or several segments.Additionally, the client device 102 is operable to provide the externalA/V device information to the back office infrastructure 122 as part ofits session request in order to enable or facilitate a management node,e.g., a streaming policy server, along with a bandwidth scheduler, toeffectuate a number of streaming policy management operations, such as,e.g., determining, provisioning and allocating a bandwidth or setting abandwidth capacity limitation, determining/assigning a suitable priorityweights for streaming requested content, determining an appropriateversion of the particular content program for streaming, and the like.

FIG. 1B depicts an example network arrangement 100B that illustrates acustomer premises 152 having one or more ABR streaming clients and aplurality of network elements that may be configured to manage conflictresolution in an ABR streaming environment with respect to a bandwidthpipe 160 serving the customer premises 152. It should be appreciated byone skilled in the art that in some aspects the example networkarrangement 100B is another realization of the ABR streaming networkenvironment 100A shown in FIG. 1A. By way of illustration, customerpremises 152 may include a plurality of users 154 operating one or moreclient devices 156 (e.g., STB units 156-1, PC/tablets 156-2, smartphones156-3 and TV/DVD/Gaming consoles 156-4, etc.), that exemplify UE devices102 in HG. 1A, wherein each client device may be configured to executeone or more ABR client applications 158 for purposes of streamingcontent (i.e., as ABR clients) from one or more content servers. Aplurality of streaming sessions 162-1 to 162-N are illustrative of thesessions launched by at least a subset of the users 154 usingappropriate combinations of client devices 156 and streaming clients158, which sessions may involve content streams at different bitrates orbandwidth depending on the type of content, devices, priority weightsassociated therewith, and/or other subscriber/operator policiesimplemented as part of a bandwidth allocation and pipe management system170. Typically, priority users or users streaming priority content maybe allowed to have more bandwidth than non-priority users, for example,within the bandwidth pipe 160 serving the premises 152. When a newsession request 164 is initiated, for example, by a new clientapplication running on the same client device or on a new client device,a conflict detection mechanism 166 is operative to detect if there isany bandwidth conflict with respect to one or more clients. In oneexample implementation, a virtual simulation of the bandwidthconsumption through the pipe may be performed using, for instance aWFQ-based or similar bandwidth management system, assuming the newclient (with it's own specific requirements) being added. If anyconflict is detected (e.g., bandwidth policy requirements of one or moreclients applications is predicted to be unmet if the new client were tobe added), a conflict resolution policy mechanism 168 is operative toeffectuate certain actions to address the impending potential bandwidthconflict according to one or more embodiments of the present patentapplication as will be set forth in additional detail below.

FIGS. 2-5 depict flowcharts of various blocks, steps and/or acts thatmay be combined in one or more arrangements that illustrate exampleconflict detection and resolution methods according to one or moreembodiments of the present patent disclosure. In FIG. 2, referencenumeral 200 generally refers to at least a portion of a conflictdetection process in one embodiment. At block 202, a session requestfrom a new ABR client launched in a customer premises that includes oneor more existing ABR clients (i.e., ABR clients currently engaged incorresponding streaming sessions) is received in an example streamingnetwork environment. At block 204, a forecasting mechanism is initiatedwhereby bandwidth requirements for one or more ABR clients, includingthe existing ABR clients as well as the new ABR client in one exampleimplementation, are modeled, simulated or otherwise estimated upontaking into account a bandwidth requirement for the requested session bythe new ABR client. As pointed out previously, a virtual simulationusing WFQ techniques or similar bandwidth management system set forth inone or more related, commonly-assigned patent applications referencedhereinabove may be utilized in effectuating the forecasting mechanism.Furthermore, an example forecasting mechanism may incorporate A/V devicedisplay information relative to where the requested session will berendered, provided such information is made available, e.g., via thesession request. If any forecasted bandwidth requirements violate apolicy regarding the users, streaming session bitrate requirements orbandwidth thresholds, QoS, or any combination thereof, a potentialconflict may be detected or otherwise determined (block 206). If nopotential conflict is determined to exist, a new streaming sessionpursuant to the session request may be established with the new clientin any known or heretofore unknown streaming techniques (block 206).

FIG. 3 depicts an example conflict notification mechanism 300 that maybe utilized where a generic or legacy ABR client launches a new sessionrequest. Responsive to detecting or otherwise determining that animpending conflict exists as set forth in the flowchart of FIG. 2, aconflict notification message may be generated (block 302) at a suitablelocation within the ABR back office infrastructure as will be set forthin detail below. Broadly, the conflict notification message may comprisea video-encoded still image of a message (text, graphics, etc.) to theeffect that the session request from the new ABR client is beingrejected on account of a bandwidth conflict relative to the premises.For instance, such a message may indicate the total number of existingsessions in addition to the text that there is not enough bandwidth towatch the requested content. The video-encoded still image, which may beencoded at a low bitrate, may be provided or otherwise delivered to thenew client for display on a designated A/V device, in addition to thenew client's session request being rejected (block 306). Referencenumeral 400 shown in FIG. 4 generally refers to at least a portion ofblocks, steps and/or acts that may be involved in the delivery of avideo-encoded still message for purposes of conflict notificationaccording to one embodiment. An ABR back office is operative to send aHyperText Transfer Protocol (HTTP) message (e.g., http redirect message)to the new ABR client whose session request is rejected (block 402).Responsive to the redirect message, the new ABR client obtains amanifest file including the URL(s) corresponding to the encoded conflictnotification message (block 404). Subsequently, the new ABR clientobtains the encoded conflict notification message segments based on theURL(s) indicated in the manifest the, which are then rendered on adisplay device associated therewith (block 406).

FIG. 5 depicts an example conflict resolution mechanism 500 that may beutilized where a custom ABR client having interactive capabilitieslaunches a new session request. Responsive to detecting or otherwisedetermining that an impending conflict exists regarding the sessionrequest as set forth in FIG. 2, an interactive session may be launchedwith the new ABR client and/or one or more existing ABR clients (e.g.,if they are also custom clients having interactivity) (block 502) inrespect of the session request. As set forth at block 504, a dialog ormessage box having pull-down menus, query/response options, etc., may bepresented to the user(s) over the Internet, wherein a number of options,choices, actions, etc. may be offered to the users. For example, the newABR client user may be presented with the total number of currentlyactive streaming sessions, identity of users and/or client devicesassociated with the streaming sessions, particular content beingstreamed, priority/preference levels, etc., in addition to an option toselect one or more existing clients to terminate or otherwise deactivatethe streaming sessions associated therewith. Yet another option mayinvolve offering a point-of-sale purchase transaction to the userwhereby the user can choose to purchase a specific bandwidth upgrade(e.g., for a time period or for the duration of the particular contentrequested, etc.). Upon accepting an option input by the user, andresponsive thereto, a suitable action may be effectuated with respect tothe session request (block 506). By way of example, a new session may beestablished if the option input by the user allows for streaming of therequested content after disconnecting a selected existing sessionwithout violating the bandwidth requirements of the existing sessions(block 506).

It should be appreciated that the foregoing blocks, steps and/or acts ofFIGS. 2-5 may be arranged or re-arranged in several combinations, whichmay be executed at different locations or at co-located network elementsor nodes within a streaming network environment such as the examplenetwork environments illustrated in FIGS. 1A and 1B. Additional detailswith respect to one or more of such embodiments may be exemplified inview of FIGS. 6-13 described below.

Taking reference to FIG. 6, an example subscriber home premises 602includes a plurality of client devices, e,g., devices 604-1 to 604-5,engaged in respective streaming sessions in an ABR streaming environment600, wherein an 8 Mbs virtual pipe 622 is operative to serve thepremises 602 via a suitable gateway 614. By way of illustration, device604-1 may be a tablet having a streaming session 606-1 for contenthaving a priority level 3; device 604-2 may be a Blu-Ray Disc (BD)player coupled to a 1080p TV display and having a streaming session606-2 for content having a priority level 1; device 604-3 may be anotherBD player coupled to a 720p TV display and having a streaming session606-3 for content having a priority level 2; device 604-4 may be aset-top box (STB) coupled to a 480i TV display and having a streamingsession 606-4 for content having a priority level 3; and device 604-5may be a smartphone having a streaming session 606-5 for content havinga priority level 4. A subscriber/operator ABR policy management node orsystem 618 may be configured to maintain appropriate priority-to-weightmapping relationships that may be used in bandwidth scheduling, asillustrated by Table 1 below:

TABLE I Priority Level Weight Priority 1 3.0 Priority 2 1.75 Priority 30.875 Priority 4 0.4375The subscriber/operator ABR policy management node 618 may also maintaina messaging delivery policy that assigns a relatively low messagingweight (e.g., weight 0.2) with respect to message transmission. Further,a bitrate threshold policy may establish a defined minimum video bitratethreshold of 0.4 Mbs that may be applied across all priority levels andweights. Additionally or alternatively, the bitrate threshold policy maycomprise a more sophisticated approach wherein differentpriorities/weights may be accorded varying thresholds. For example, ahigher video bitrate threshold may be established for high prioritysessions in contrast to lower priority sessions that may havecorrespondingly lower bitrate thresholds, or vice versa.

Subscriber premises 602 also includes a client device 608, e.g., a PS3gaming device coupled to a 1080p TV display, operative to request ABRassets from one or more content providers. When a new session request628 is launched by device 608, it is propagated via gateway 614 to aback office 616 as exemplified by the request 630 that may include theconnected TV display's DDI such as, including but not limited to,make/manufacture of the gaming device and connected display, resolution(e.g., 720p, 1080p, etc.), class/size (e.g., 52″, 62″, 73″, etc.), andthe like. Responsive thereto, a session ID (e.g., Session ID: XXX) maybe assigned with respect to the new session request, which may betransmitted to the subscriber/operator ABR policy management node 618via a policy management request 640. In an example implementation, thepolicy management request 640 may also include the requestingdevice/display information received as part of the session request 630.Service logic executing at the subscriber/operator ABR policy managementnode 618 may be configured to generate, responsive to the policymanagement request 640 received from the back office node 616, a bitrateforecasting request 634 to a forecasting module that may be implementedat different locations with respect to the ABR streaming environment600. As will be described in detail below, such a forecasting module maybe provided as part of a premises gateway or a CON edge/delivery node.For purposes of FIG. 6, an ABR delivery server functionality 620 thatfacilitates the WFQ-based bandwidth pipe 622 serving the premises 602 isexemplified as having the bitrate forecasting capability. By way ofillustration, the ABR delivery server functionality 620 is operative tomanage a plurality of streams of different bandwidth comprising thebandwidth pipe 622 that correspond to the existing sessions of theclient devices 604-1 to 604-5 (e.g., five streams represented by arrowsof varying thickness, denoting bandwidths 1.009 Mbs, 3.459 Mbs, 2.018Mbs, 1.009 Mbs and 0.504 Mbs, which reflect the differentpriority/weight factors associated with the respective sessions).

Appropriate forecasting logic executing at the ABR delivery serverfunctionality 620 may be configured to generate a bitrate forecastresponse 636 to the operator/subscriber ABR policy management node 618that includes various bitrates forecasted for the current as well as therequested sessions. Tables II and III below are illustrative of thevarious pieces of information that may be provided as part of an examplea bitrate forecast response 636:

TABLE II Current Sessions Session ID Device/Display Weight BitrateCurrent session ID 1 Device-1 3.0 2.425 Mbs  Current session ID 2Device-2 1.75 1.409 Mbs  Current session ID 3 Device-3 .875 .704 MbsCurrent session ID 4 Device-4 .875 .704 Mbs Current session ID 5Device-5 .4375 .352 Mbs

TABLE III New Session Request Session ID Device/Display Weight BitrateSession ID XXX PS3/HDTV 3.0 2.415 Mbs

Responsive to receiving the bitrate forecast response 636, theoperator/subscriber ABR policy manager node 618 is operative to detector otherwise determine whether there is an impending conflict withrespect to the new session request. For example, if the defined minimumvideo bitrate threshold is 0.4 Mbs, it can be seen that the forecastedbitrate for the streaming session ID 5 is below that threshold afteraccounting for the new session. Accordingly, a determination may be madethat a potential conflict exists pursuant to the new session request.Thereafter, the operator/subscriber ABR policy management node 618 isoperative to generate one or more notifications or responses dependingon how an embodiment of conflict management/resolution functionality maybe distributed or localized within the ABR network. Illustratively, aseparate conflict management node 624 may be provided that is configuredto receive a notification 638 (e.g., “User Bitrate Exceeded”notification) that includes the various pieces of information receivedfrom the forecasting functionality. Further, the operator/subscriber ABRpolicy management node 618 may also be configured to generate a policymanagement response 632 to the back office node 616, which includes anindication that there is a potential conflict with respect to the newsession request (having the Session ID XXX).

FIG. 7 depicts a flowchart of various blocks, steps and/or actsillustrative of additional details with respect to an embodiment of aconflict detection scheme 700 in view of the example ABR streamingenvironment 600 described above. At block 702, a new client makes an ABRsession request to a back office, which assigns a session ID thereto(block 704). The back office requests a policy for the new client fromthe subscriber/operator policy management system or policy manager(block 706). Responsive thereto, the subscriber/operator policymanagement system generates a request to an ABR delivery server/systemfor forecasted bitrate information, wherein the request includes the newclient session ID and policy weighting information for the requestedsession (block 708). The ABR delivery server responds to the policymanager with forecasted bitrates based on network simulation etc. thatincludes a weight assigned to the new client's session (block 710). Adetermination may be made as to whether any forecasted bitrates areoutside audio and/or video delivery thresholds (block 712). If there isno violation of the applicable thresholds, the back office may generatea response to the new client including a suitable ABR session setupsequence (e.g., providing one or more manifest files including URLs tothe requested content), as set forth at block 718. Otherwise, the policymanager informs a conflict manager node and the back office nodeappropriately (blocks 714 and 716), as described above.

FIG. 8 depicts an example ABR streaming environment 800 with additionaldetails relative to an embodiment of a conflict resolution/managementscheme according to the teachings of the present patent disclosure. Aswill be realized by one skilled in the art, the example ABR streamingenvironment is substantially similar to the streaming environment 600 ofFIG. 6 described above. Accordingly, at least certain portions of thedescription of FIG. 6 are equally applicable with respect to thestreaming environment 800, mutatis mutandis. Focusing on the aspectsrelating to conflict resolution after a potential conflict has beendetected, the example embodiment of FIG. 8 is illustrative of thescenario where a video-encoded still image of a conflict notificationmessage may be provided to the requesting new client 608 of subscriberpremises 602. Upon receiving a potential conflict notification includingvarious pieces of forecasted bitrate information with respect to a newsession request (as exemplified by reference numerals 808 and 810) fromthe operator/subscriber policy manager 618, the ABR conflict managementnode 624 is operative to transmit an encode message request 816 to anABR video messaging system or node 802 for generating and encoding asuitable conflict notification message. A still image containing theconflict notification message (e.g., “Your home has Five ABR videosessions active. There is not enough bandwidth to watch your video.”)may be encoded using an appropriate video bitrate that is sufficientlylow such that its streaming to the client device via bandwidth pipe 622does not impact the quality of the existing sessions. An appropriatemechanism (e.g., Kush Gauge calculation) may be utilized by a conflictnotification messaging component 806 associated with the video messagingnode 802 for computing a bitrate used in generating the video-encodedimage of the conflict notification message that may be stored at adatabase 804, including its manifest and video message segmentstherefor. An encode message response 812 may be provided to the conflictmanagement node 624 including a URL to the message manifest, which ispropagated to the back office 616, as indicated by a response message818 containing the requested session's ID (e.g., Session ID: XXX asreferenced in the description of FIG. 6 above). The back office 616thereafter generates a notification 821 to the operator/subscriberpolicy manager node 618, in addition to transmitting an HTTP redirectmessage to premises gateway 614, (e.g., using an http response statuscode 302 that includes a URL in its location header field for thenotification message manifest), which is propagated to the new clientdevice 608, as illustrated by reference numeral 828. Messages 830, 824are illustrative of the http message propagated to the video messagingnode 802 for requesting the manifest (e.g.,http://xxx.xxx.xxx.xxx/message/manifest.xxx) and messages 826, 838 areillustrative a response message including the manifest from the videomessaging node received by the client device 608. Responsive to thereceived message manifest file, the new client 608 is operative toreceive the video-encoded image of the conflict notification message,based on the interaction of the video messaging server 802,operator/subscriber policy manager node 618 and the delivery server 620,as a separate stream 836 of the bandwidth pipe 622. Pursuant to thisinteraction, the delivery server 620 receives via path 832 encoded videomessage segments of the conflict notification message from the videomessaging node 802 and applicable data (e.g., subscriber device data,session ID and a weight associated with the notification message stream836) via a notification 834 from the operator/subscriber policy managernode 618. As the conflict notification message stream 836 is propagatedvia gateway 614 to the client device 608 (as a streaming session 840having a low bandwidth, e.g., 0.2239 Mbs), the image may be rendered atthe connected HDTV display that shows the message: Your home has FiveABR video sessions active. There is not enough bandwidth to watch yourvideo. In an example implementation, as the message image is beingdisplayed on the connected display device, the new client applicationmay remain active although its new session request has been rejected bythe back office 616.

FIG. 9 depicts a flowchart of various blocks, steps and/or actsillustrative of additional details with respect to an embodiment of aconflict resolution scheme 900 in view of the example ABR streamingenvironment 800 described above. Responsive to a conflict detectionmechanism (block 902), a conflict management system or node sends amessage encode request to an ABR video messaging server/system (block904). An image of a suitable conflict notification message is generated,which is then video-encoded (block 908), e.g., using a single bitrate,based on a Kush Gauge calculation for bitrate computation, asexemplified below:

Bitrate in kbps=pixel count×motion factor (1, 2, or 4)×0.07/1000;

where the pixel count is the multiple of the video's width and height,the motion factor is an estimate of how fast the moving images are in avideo. For an example message in Full SD resolution of 780×480, with astill image motion factor being 1, the expression computes to 24.192kbps, which may applied for encoding the still image into video. Itshould be appreciated that low bitrates of up to 50 kbps may be used intypical legacy streaming client applications for inserting avideo-encoded sill image of appropriate conflict notificationmessage(s).

At block 910, the video messaging server responds to the conflictmanagement system with an ABR manifest referencing the still imagemessage encoded into video using the single bit rate computed accordingto the Kush Gauge calculation. At block 912, the conflict managementnode informs the back office of the conflict notification messagemanifest associated with the session ID generating the potentialconflict. Thereafter, the back office sends an ABR message notificationto the operator/subscriber policy management node including thesubscriber, client device and session ID (block 914), which ispropagated to a WFQing delivery server in a notification that alsoincludes a suitable weighting factor for the delivery of the message(block 916). The back office further responds to the requesting ABRclient with an http 302 redirect message, referencing the ABR encodedconflict notification message (block 918). Responsive thereto, theconflicting client device pulls the ABR video message segments forrendering on a display screen (block 920).

FIG. 10 depicts an example ABR streaming environment 1000 withadditional details relative to another embodiment of a conflictresolution/management scheme according to the teachings of the presentpatent disclosure. As before, the description of the streamingenvironments shown in FIGS. 6 and 8 is substantially applicable withrespect to the streaming environment 1000, mutatis mutandis.Accordingly, focusing primarily on the aspects relating to conflictresolution after a potential conflict has been detected, the exampleembodiment of FIG. 10 is illustrative of the scenario where aninteractive session may be launched with the conflicting new clientand/or other existing clients having custom/interactive capabilities.Upon receiving a potential conflict notification including variouspieces of forecasted bitrate information with respect to a new sessionrequest (as exemplified by reference numerals 808 and 1008), the ABRconflict management node 624 is operative to initiate an interactivesession with the new client 608 (e.g., via the Internet) whereby acustomized message dialog box may be provided for facilitating userselection with respect to a variety of options, actions, etc. A customclient messaging (CCM) module 1002 associated with the ABR conflictmanagement node 624 may be provided to generate an example dialog box1006 that allows for selecting an existing video session to terminate.As described previously, other options may also be provided for userselection depending on a specific implementation. Reference numerals1012 and 1014 in FIG. 9 are illustrative of an interactive sessionwherein the user of the client device 608 selects a particular existingsession, e.g., OTT STB session with client device 604-4, fortermination. Responsive to user selection message 1014, the ABR conflictmanager node 624 generates a client disconnect message 1016 to the OTTSTB client 604-4. In addition, the ABR conflict manager node 624 alsosends a disconnect decision message 1010 to the back office 616 thatreferences the client device identified for disconnection as well as theSession ID.

FIG. 11 depicts a flowchart of various blocks, steps and/or actsillustrative of additional details with respect to an embodiment of aconflict resolution scheme 1100 in view of the example ABR streamingenvironment 1000 described above. Responsive to a conflict detectionmechanism (block 1102), a conflict management system or node sends aninteractive session message to the conflicting ABR client (block 1104),whereby a user of the client may input a suitable selection (block1106). If no user action is taken, the ABR client returns to itspre-request state (block 1108). On the other hand, if a terminationaction is selected by the user, which may involve selecting more thanone existing session for termination, the conflict management systemreceives the user input via a suitable disconnect message (block 1110).Responsive thereto, the client management system may send one or moreclient disconnect messages to the existing clients (block 1112),whereupon a new ABR session setup message may be sent to the back officefor setting up the requested session (block 1114). It should beappreciated that a new ABR session setup message may be generated onlywhen it has been ascertained that the terminated session frees up enoughbandwidth such that adding the new session would not cause a conflict.Accordingly, in one further variation, an iterative selection andconflict verification scheme may be provided wherein a user mayinteractively select different sessions one by one for termination untilappropriate bandwidth is released for accommodating the new session.Additionally, the conflict management system may be configured to sendone or more disconnect session messages to the back office, as explainedhereinabove (block 1116). Furthermore, if other actions are taken by theuser in lieu of a termination action, e.g., a bandwidth purchase action,appropriate responses may then be effectuated by the system, asdescribed previously.

Turning to FIG. 12, depicted therein is an example ABR streamingenvironment 1200 that is substantially similar to the streamingenvironment of FIG. 6, wherein certain aspects of conflictdetection/resolution may be practiced at a premises gateway 1208. In theembodiment of FIG. 12, appropriate bitrate forecasting functionality maybe provided as part of gateway 1208 operative to manage an incoming ABRdelivery or broad band pipe 1202 such that an outbound dynamic virtualpipe 1204 of suitable capacity is made available for consumption by theexisting clients 604-1 to 604-5 and new client 608. Focusing on thevarious interactive functionalities of the streaming environment 1200,when the new client 608 initiates a session request 1206, gateway 1208is configured to propagate the request to the back office 616, asexemplified by a message 1212 that includes the device, connecteddisplay information, etc. Responsive to appropriate policy managementrequest/response interfacing with the back office 616, theoperator/subscriber policy manager node 618 is operative to generate abitrate forecast request 1214 to gateway 1208. Substantively similar tothe forecast request 634 described previously with respect to thestreaming environment 600 of FIG. 6, the bitrate forecast request 1214may include the new client ID, device/display combination, in additionto appropriate priority/weight values associated with the requestedsession. Responsive thereto, the forecasting functionality executing atgateway 1208 is operative to generate a bitrate forecast responsemessage 1216 similar to the bitrate forecast response 636 that includesvarious pieces of information, e.g., session IDs, predicted bitrates,etc., relative to the ongoing sessions as well as the requested session.Thereafter, appropriate interfacing among the operator/subscriber policymanager 618, conflict management node 624 and back office 616, iseffectuated for purposes of conflict detection and resolution, asdescribed hereinabove.

FIG. 13 depicts an example ABR streaming environment 1300 that issubstantially similar to the streaming environment of FIG. 6, whereincertain aspects of conflict detection/resolution may be practiced at aCDN node 1318. In the embodiment of FIG. 13, appropriate bitrateforecasting functionality may be provided as part of an edge/deliverynode such as, e.g., node 1318, that serves to provide a dynamic virtualbandwidth pipe 1340 of suitable capacity with respect the customerpremises 602 via a premises gateway 1322. Reference numerals 1310 and1312 refer to a redirector node and a central origin server node,respectively, of CDN 1302, which includes a plurality of regional nodes,e.g., nodes 1314, 1316, coupled to the central server 1312. Further, theedge/delivery node 1318 is hierarchically coupled to the regional node1316. Focusing on the various interactive functionalities of thestreaming environment 1300, when the new client 608 initiates a sessionrequest 1304, gateway 1322 is configured to propagate the request to theback office 616, as described previously. Pursuant to appropriate policymanagement request/response interfacing with the back office 616, theoperator/subscriber policy manager node 618 is operative to initiallydetermine the location of the edge/delivery node 1318 by engaging in aquery mechanism 1330 with the redirector node 1310 of CDN 1302. Uponidentifying the edge/delivery node 1318 (e.g., Atlanta, Ga.) serving thecustomer premises 602, a response including the nodal location isprovided to the operator/subscriber policy manager node 618. Thereafter,a bitrate forecast request 1334 is generated to the edge/delivery node1318, substantively similar to the forecast requests 634, 1214 describedpreviously with respect to the streaming environment 600, 1200 of FIGS,6 and 12, respectively. Responsive thereto, the forecastingfunctionality executing at the CDN node 1318 is operative to generate abitrate forecast response message 1336 similar to the bitrate forecastresponses 636 and 1216. As before, appropriate interfacing among theoperator/subscriber policy manager 618, conflict management node 624 andback office 616, is effectuated for purposes of conflict detection andresolution in accordance with the teachings hereinabove.

FIG. 14 depicts a block diagram of an example element or component 1400that may be configured to execute certain aspects of conflictdetection/resolution according to one or more embodiments of the presentpatent application. In one arrangement, component 1400 is illustrativeof a CDN node (e.g., edge node 1318) that includes a bitrate forecastmodule 1406 and a bandwidth scheduling and pipe management module 1412,e.g., based on WFQ techniques. In another arrangement, component 1400 isillustrative of a customer premises gateway (e.g., 1208) including thebitrate forecasting module 1406. To the extent such a gateway isoperative to manage scheduling of an outbound bandwidth pipe serving thecustomer premises, it may also include a suitable WFQ-based bandwidthpipe management module 1412. As will be appreciated by one skilled inthe art, the functionality of bitrate forecasting may be provided aspart of a persistent memory (e.g., non-volatile memory, which maycomprise part of a generalized memory subsystem 1404), havingappropriate program instructions or code portions that may be executedby one or more processors 1402. In one embodiment, the bitrateforecasting module 1406 may be configured to perform, under control ofprocessors 1402: forecast bandwidth requirements, responsive to arequest from a operator/subscriber policy management node, for one ormore existing ABR clients of customer premises 602 with respect tocorresponding ABR streaming sessions after accounting for a bandwidthrequirement of a new ABR client's request for initiating a new streamingsession on a client device; and generate a bandwidth forecast responsemessage to the subscriber policy management node. As described above,the bandwidth forecast response message includes bitrates forecasted forthe existing ABR streaming sessions and the requested new streamingsession based at least in part upon priority weights associated with theexisting ABR streaming sessions and the requested new streaming session.Appropriate transceiver (Tx/Rx) interfacing 1408 may be provided as partof component 1400 to facilitate bitrate forecast request/responsemessaging. Additional interfacing 1410 may also be provided depending onwhether component 1400 is arranged as premises gateway 1208 or CDN node1318.

Based upon the foregoing Detailed Description, it should be appreciatedthat one or more embodiments of the present disclosure can beadvantageously implemented in a number of ABR applications, includinglegacy client applications as well as custom client applications. Inaddition to allowing the users to override standing policies,embodiments herein may facilitate control of how conflicts in policiesare notified and resolved.

In the above-description of various embodiments of the presentdisclosure, it is to be understood that the terminology used herein isfor the purpose of describing particular embodiments only and is notintended to be limiting of the invention. Unless otherwise defined, allterms (including technical and scientific terms) used herein have thesame meaning as commonly understood by one of ordinary skill in the artto which this invention belongs. It will be further understood thatterms, such as those defined in commonly used dictionaries, should beinterpreted as having a meaning that is consistent with their meaning inthe context of this specification and the relevant art and may not beinterpreted in an idealized or overly formal sense expressly so definedherein.

At least some example embodiments are described herein with reference toblock diagrams and/or flowchart illustrations of computer-implementedmethods, apparatus (systems and/or devices) and/or computer programproducts. It is understood that a block of the block diagrams and/orflowchart illustrations, and combinations of blocks in the blockdiagrams and/or flowchart illustrations, can be implemented by computerprogram instructions that are performed by one or more computercircuits. Such computer program instructions may be provided to aprocessor circuit of a general purpose computer circuit, special purposecomputer circuit, and/or other programmable data processing circuit toproduce a machine, so that the instructions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, transform and control transistors, values stored in memorylocations, and other hardware components within such circuitry toimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks, and thereby create means (functionality)and/or structure for implementing the functions/acts specified in theblock diagrams and/or flowchart block(s). Additionally, the computerprogram instructions may also be stored in a tangible computer-readablemedium that can direct a computer or other programmable data processingapparatus to function in a particular manner, such that the instructionsstored in the computer-readable medium produce an article of manufactureincluding instructions which implement the functions/acts specified inthe block diagrams and/or flowchart block or blocks.

As alluded to previously, tangible, non-transitory computer-readablemedium may include an electronic, magnetic, optical, electromagnetic, orsemiconductor data storage system, apparatus, or device. More specificexamples of the computer-readable medium would include the following: aportable computer diskette, a random access memory (RAM) circuit, aread-only memory (ROM) circuit, an erasable programmable read-onlymemory (EPROM or Rash memory) circuit, a portable compact disc read-onlymemory (CD-ROM), and a portable digital video disc read-only memory(DVD/Blu-ray). The computer program instructions may also be loaded ontoor otherwise downloaded to a computer and/or other programmable dataprocessing apparatus to cause a series of operational steps to beperformed on the computer and/or other programmable apparatus to producea computer-implemented process such that the instructions which executeon the computer or other programmable apparatus provide steps forimplementing the functions/acts specified in the block diagrams and/orflowchart block or blocks. Accordingly, embodiments of the presentinvention may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.) that runs on a processorsuch as a digital signal processor, which may collectively be referredto as “circuitry,” “a module” or variants thereof.

Further, in at least some additional or alternative implementations, thefunctions/acts described in the blocks may occur out of the order shownin the flowcharts. For example, two blocks shown in succession may infact be executed substantially concurrently or the blocks may sometimesbe executed in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. For example, at leastsome of the nodes shown in the streaming network environment of FIG. 6such as the operator/subscriber policy manager, back office, andconflict management, or example, may be integrated or otherwiseco-located in different combinations. Finally, other blocks may beadded/inserted between the blocks that are illustrated. Moreover,although some of the diagrams include arrows on communication paths toshow a primary direction of communication, it is to be understood thatcommunication may occur in the opposite direction relative to thedepicted arrows.

Although various embodiments have been shown and described in detail,the claims are not limited to any particular embodiment or example. Noneof the above Detailed Description should be read as implying that anyparticular component, element, step, act, or function is essential suchthat it must be included in the scope of the claims. Reference to anelement in the singular is not intended to mean “one and only one”unless explicitly so stated, but rather “one or more.” All structuraland functional equivalents to the elements of the above-describedembodiments that are known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the present claims. Accordingly, those skilled in the artwill recognize that the exemplary embodiments described herein can bepracticed with various modifications and alterations within the spiritand scope of the claims appended below.

What is claimed is:
 1. A method for managing conflict resolution in anadaptive bitrate (ABR) streaming environment with respect to a bandwidthpipe serving a customer premises, the method, comprising: receiving asession request from a new ABR client launched in the customer premisesthat includes one or more existing ABR clients, wherein each existingABR client is engaged in a corresponding ABR streaming session;forecasting bandwidth requirements for the one or more existing ABRclients with respect to the corresponding ABR streaming sessions afteraccounting for a bandwidth requirement for the new ABR client's sessionrequest; detecting a conflict if any of forecasted bandwidthrequirements violates a bitrate threshold policy relative to thecorresponding ABR streaming sessions of the existing ABR clients; and ifthere is a conflict, providing a conflict notification message to thenew ABR client and rejecting the session request from the new ABRclient.
 2. The method as recited in claim 1, wherein the conflictnotification message comprises a video-encoded still image of a messagethat the session request from the new ABR client is being rejected onaccount of a bandwidth conflict.
 3. The method as recited in claim 2,wherein the still image is encoded at a particular bitrate.
 4. Themethod as recited in claim 3, wherein the particular bitrate forencoding the still image is computed using a Kush Gauge calculation. 5.The method as recited in claim 2, wherein the conflict notificationmessage is provided to the new ABR client by way of a HyperText TransferProtocol (HTTP) redirect message generated by an ABR back office thatincludes a manifest URL for the video-encoded still image.
 6. The methodas recited in claim 1, further comprising: determining that there is noconflict relative to the session request from the new ABR client: andsetting up a new streaming session responsive to the session requestfrom the new ABR client.
 7. The method as recited in claim 1, whereinthe session request from the new ABR client includes display deviceinformation associated with an external audio/video (A/V) device forrendering content to be streamed.
 8. The method as recited in claim 1,wherein the forecasting of bandwidth requirements is performed at apremises gateway responsive to a forecasting request from a subscriberpolicy management node.
 9. The method as recited in claim 1, wherein theforecasting of bandwidth requirements is performed at a content deliverynetwork (CDN) edge delivery node responsive to a forecasting requestfrom a subscriber policy management node.
 10. A system for managingconflict resolution in an adaptive bitrate (ABR) streaming environmentwith respect to a bandwidth pipe serving a customer premises, the systemcomprising: a back office operative to receive a session request from anew ABR client launched by a client device in the customer premises thatincludes one or more existing ABR clients, wherein each existing ABRclient is engaged in a corresponding ABR streaming session; a subscriberpolicy management node operative to request, responsive to a messagefrom the back office, one of a premises gateway and a CDN edge deliverynode for forecasted bandwidth requirements of the one or more existingABR clients with respect to the corresponding ABR streaming sessionsafter accounting for a bandwidth requirement for the new ABR client'ssession request, the subscriber policy management node further operativeto detect a conflict if any of forecasted bandwidth requirementsviolates a bitrate threshold policy relative to the corresponding ABRstreaming sessions of the existing ABR clients; and a conflictmanagement node operative, responsive to a conflict detection messagefrom the subscriber policy management node, to generate a conflictmessage encoding request to a video message system for facilitatingtransmission of a still image of a conflict notification message to thenew ABR client that the session request from the new ABR client is beingrejected on account of a bandwidth conflict.
 11. The system as recitedin claim 10, wherein the still image is video-encoded at a particularbitrate.
 12. The system as recited in claim 11, wherein the particularbitrate for encoding the still image is computed using a Kush Gaugecalculation.
 13. The system as recited in claim 12, wherein the encodedstill image of the conflict notification message is provided to the newABR client by way of a HyperText Transfer Protocol (HTTP) redirectmessage generated by the back office that includes a manifest URL forthe video-encoded still image.
 14. The system as recited in claim 10,wherein the session request from the new ABR client includes displaydevice information associated with an external audio/video (A/V) devicefor rendering content to be streamed.
 15. A premises gateway configuredto manage a bandwidth pipe serving a customer premises, the premisesgateway comprising: one or more processors; and a bitrate forecastingmodule coupled to the one or more processors, wherein the bitrateforecasting module includes instructions executable by one or moreprocessors and configured to: forecast bandwidth requirements,responsive to a request from a subscriber policy management node, forone or more existing ABR clients of a customer premises with respect tocorresponding ABR streaming sessions after accounting for a bandwidthrequirement of a new ABR client's request for initiating a new streamingsession on a client device; and generate a bandwidth forecast responsemessage to the subscriber policy management node, the bandwidth forecastresponse message including bitrates forecasted for the existing ABRstreaming sessions and the requested new streaming session based atleast in part upon priority weights associated with the existing ABRstreaming sessions and the requested new streaming session.
 16. Thepremises gateway as recited in claim 15, wherein the new ABR client'srequest for initiating a new streaming session request includes displaydevice information associated with an external audio/video (A/V) devicefor rendering content to be streamed.
 17. An edge delivery node disposedin a content delivery network (CDN) and configured to manage a bandwidthpipe serving a customer premises, the edge delivery node comprising: oneor more processors; and a bitrate forecasting module coupled to the oneor more processors, wherein the bitrate forecasting module includesinstructions executable by one or more processors (1402) and configuredto: forecast bandwidth requirements, responsive to a request from asubscriber policy management node, for one or more existing ABR clientsof a customer premises with respect to corresponding ABR streamingsessions after accounting for a bandwidth requirement of a new ABRclient's request for initiating a new streaming session on a clientdevice; and generate a bandwidth forecast response message to thesubscriber policy management node, the bandwidth forecast responsemessage including bitrates forecasted for the existing ABR streamingsessions and the requested new streaming session based at least in partupon priority weights associated with the existing ABR streamingsessions and the requested new streaming session.
 18. The edge deliverynode as recited in claim 17, wherein the new ABR client's request forinitiating a new streaming session request includes display deviceinformation associated with an external audio/video (A/V) device forrendering content to be streamed.
 19. The edge delivery node as recitedin claim 17, wherein the request from the subscriber policy managementnode is received after a query by the subscriber policy management nodeto a redirector node disposed in the CDN, the query for determining theedge delivery node managing the bandwidth pipe associated with thecustomer premises.
 20. The edge delivery node as recited in claim 17,further comprising a bandwidth allocation and pipe management module forallocating bandwidth to the customer premises using weighed fair queuing(WFQ) with respect to the ABR streaming sessions.